There's a bit of a risk of having some divergence between the cli code and the activities code, we generally try to call an activity from here even if that means it's async.

All that being said I'm fine with having a direct implementation. Any chance we can dry a bit these 2 commands?

yep I agree, I was contemplating adding a new activity but in the end we won't do that in the workflow (upsert and check parents right after)

Could be an option on the activity + a new workflow to do just one page with that option set

hmm interesting

sounds good, doing that 👍

actually it's a bit too convoluted to use the same activity: one fetches the page + upserts without parent and is optimized for the workflow (it does some version checking), the other one fetches the page, fetches the space using the page data, resolves parents and does an upsert with parents.

I added a separate activity to do the upsertWithFullParents and added workflows since we might want to do these with retries and history
SGTY @spolu ?

Yess!